Changes in paths and avoid move operation risks #11
Conversation
|
Hi Jose, Thank you very much for your contribution. I'm sorry for not responding in a timely manner - I did not get notified at all that you created this PR, not sure why. This looks great at a first glance - I'll take a look at it over the weekend and test it out. I haven't shown this project much love in a while. Do you think it would be useful to you/a subset of people? I was thinking whether to start working on it again, get it in better shape, and maybe share it on some tech enthusiast forums (HN, the likes). |
|
Hi Nicoleta! To be fair I was looking through some GitHub repositories and found this project, and the idea was appealing so I decided to go ahead and see where I could help a bit. I think it might be a good resource for people who have their Downloads folder too crowded |
Hello! I was taking a look at some of the issues in this repository
Regarding the issue #9, I found this discussion that states files can get corrupted if the destination folder doesn't exists
In the discussion is suggested to use this validation before actually moving a file:
Also I saw #6 and #5 and I believe the changes in how paths are created to use
os.path.joinmight help with those issues